Conversation
…e located in: /resources/css
…o be added as container model attribute in every controller that returns template view
There was a problem hiding this comment.
we can not change configuration like that, we need to figure it out how to store that localy
|
so then should we determine database name, username and password for everyone of us? so everyone would use the same data? btw. forgot to change it back sorry ;) |
|
No, we should not. I'm not familiar with spring yet but there have to be way to store local configuration or parameters. They call it profiles. |
|
the best idea is to create separated task/issue for that :) |
Conflicts: src/main/java/net/_4programmers/_4note/controllers/UsersController.java src/main/webapp/WEB-INF/views/user.ftl
There was a problem hiding this comment.
Im not sure it is good idea to surround a main content with jumbotron class :)
|
yes sure, I will send next commit for a while |
|
should I merge it to the master? |
|
If it works fine, go ahead. I'm not sure of bootstrap integration, but we can change it in any time. |
2 participants
templating idea can be changed if you have any suggestions
for now: every controller should return template.ftl and in the model an attribute "container" containing path to .ftl file should be added; look at the code, my idea quite self explaining